S4Hana to Stella System API
Support and FAQ
How do I connect to Test?
This API is a POC api and hence its not planned for TEST deployment
How do I connect to Production?
This API is a POC api and hence its not planned for Production deployment
How do I report bugs or production incidents?
This API is a POC api and hence its not planned for Production deployment
How do I request for more information?
Check out our FAQ page first! If you don’t find the answer in our FAQ or gSite, you can raise any questions via our form “Raise a question”. Please contact the API owner or Architect only in case of escalations.
A request should be raised in Service Now for any request for information or to change/update deployment configuration. These requests are sent to the MuleSoft support team.
Please find the steps to complete this here: https://rochewiki.roche.com/confluence/display/APIGOV/How+to+Create+a+Request
How do I request new features?
New API project feature(s) or API project change request (not deployment related) should be raised by creating a new demand. This demand will be sent to GIS ICC where engagement will begin.
Please find the steps to complete this here: https://sites.google.com/roche.com/gis-icc/contact-us
Contacts
| Role | Name | Role Description | Contact |
|---|---|---|---|
| API Owner | Maghesh Babu Govinda Rajulu | The API Owner is the primary person who is responsible for prioritizing the feature backlog as well as determining if approval can be granted to any new consumer. The API Owner is accountable for the SLAs, Exchange content detail and accuracy of their API in Mulesoft Exchange. API Owner also is the one who can onboard consumers. The API Owner should be contacted if formal channels of intake such as Workday,ServiceNow is not yielding timely results | maghesh_babu.govinda_rajulu@roche.com |
| API Architect | Lakshmi Priya Chellamani | API Architect is the primary person responsible for the API’s Architecture and Design. Other Solution Architects and Solution Engineers who are looking forward to reusing this asset may reach out to API Architect address any technical questions they have in case the documentation of each of the end points published in exchange via RAML is not self explanatory. | lakshmipriya.chellamani@businesspartner.roche.com |